System, An Arrangement And A Method For Providing Core Network Nodes With Mobile Station Related Information

ABSTRACT

The present invention relates to a system for providing a core network node with location related information about one or more mobile user stations accessing the core network over an access network. It comprises a number of radio access network nodes (RNC; BSC) a number of first network nodes or core network nodes serving communication of data (SGSN 1 , SGSN 2 ), a number of second core network nodes comprising gateway core network nodes (GGSN) acting as gateways to external or third party controlled data communication networks and/or service providers. Location related information of one or more mobile user stations obtained from the radio network access nodes is provided from a first network node or core network node to a second core network node. Said location related information is provided in one or more dedicated information elements added to existing communication of messages between said first core network node and said second core network node.

FIELD OF THE INVENTION

The present invention relates to a system for providing a core networknode with location related information about one or more mobile userstations accessing the core network over an access network. Theinvention also relates to a network node for a communications systemsupporting communication of packet data and also to a core network nodefor a communication system supporting communication of packet data whichacts as a gateway node to external or third party controlledcommunications systems or service providers. Still further the inventionrelates to a method for providing a second core network node acting as agateway to external or third party controlled data communicationssystems, with location related information of one or more mobile userstations accessing the core network over an access network.

STATE OF THE ART

In today known systems core network nodes, such as for example GGSNs(Gateway GPRS Support Node), do not have sufficient knowledge of wheremobile stations actually are located. It is for example known that GGSNsare provided with location information through so called CGI/SAI (CellGlobal Identifier/Service Area Identifier) from for example SGSNs(Serving GPRS Support Nodes). Today CGI/SAI information is sent to aGGSN when a mobile user station (MS), e.g. a User Equipment (UE) ismoving from an old SGSN to a new SGSN. Often, however, said informationin SGSN/GGSN is not worth so much, since the accuracy is not good due tothe fact that a mobile user station may be involved in several handoversat cell level while still being connected to one and the same SGSN, i.e.there may be several handovers at cell level before the SGSN is notified(or there is a change of SGSNs). Thus, in for example PLMNs (Public LandMobile Network) supporting GPRS services (GSM Packet Radio Service) theprecise and actual location of an MS or an UE is not known, neither bythe SGSN nor by the GGSN providing the service. The SGSN does havelocation information, but it only has information that is provided toit, which however has a limited granularity and/or a limited timeliness.The reason therefore is, as referred to above, that the MS/UE may movewithin a routing area without informing the SGSN. The occasions when theSGSN may report the location of the MS/UE to the GGSN are few, basicallyat PDP context establishment in the SGSN. Today PLMN operators forexample tend to apply Packet Switched (PS) mobile access charging in aGGSN where they apply differentiated rates depending on the serviceprovided. Thus it is a problem with today known solutions among othersas far as charging is concerned. An operator who wants to applydifferent rating, for example depending on the location of an MS/UE,will face the problem that the location information is not available inthe GGSN or that it is not accurate or timely enough.

If the Gn interface between the SGSN and the GGSN would be elaborated toreport location changes, this would involve several drawbacks. First,such an approach would lead to intensive signalling between the SGSN andGGSN still without any possibility to adapt to the requirements that canbe derived from the rating. Moreover the location granularity would bethe same for all MSs/UEs and thus the report triggering would be thesame for each MS/UE.

For several implementations, for example, relating to charging but alsofor several other implementations or services the information as to thelocation or the location at a given time is not sufficient in forexample a core network node such as a GGSN and all today known solutionsto increase the accuracy etc. of application information all suffer fromthe drawback that it requires a lot of signalling and all mobile userstations (here meant MSs and/or UEs or, more generally, mobile userstations) are treated completely equally as far as location relatedinformation is concerned.

SUMMARY OF THE INVENTION

What is needed is therefore a system as initially referred to in whichthe provisioning of location related information to core network nodesis provided for in an easy and flexible manner. Particularly a system isneeded through which the accuracy of location related information can beincreased in core network nodes, particularly in core network nodesacting as gateways to external networks or third party controlledcommunication systems. Furthermore a system is needed through whichdifferent degrees of accuracy of location related information can beprovided for different mobile user stations, i.e. that allowscontrollability.

Moreover a system is needed through which location related informationcan be provided to core network nodes in a more timely manner thanhitherto. Yet further a system is needed through which location relatedinformation can be provided to core network nodes without, or at leastwithout considerably, increasing the signalling in the system.Particularly a system is needed through which different kinds of userlocation related information can be provided to core network nodes and,advantageously also to operators and service providers or users of thirdparty controlled communication systems. Particularly a system is neededthrough which the accuracy of CGN/SAI in for example an GGSN can beincreased. Particularly a system is needed through which locationdependent charging is enabled in a better and more flexible party mannerthan hitherto. Most particularly a system is needed through which packetswitched traffic rating which is location dependent on a per mobilestation basis is allowed. Particularly a system is needed through whichit gets possible to collect location information with the appropriatelocation (and timing) related accuracy in order to perform for exampleadaptive charging or rating or adaptively and flexibly providingservices.

A (core) network node as initially referred to is also needed throughthe use of which one or more of the above mentioned objects can beachieved. Still further a core network node acting as a gateway, as alsoinitially referred to, is needed through the use of which one or more ofthe above mentioned objects can be achieved. Still further a method asinitially referred to is needed, through which one or more of the abovementioned objects can be achieved.

Therefore a system as initially referred to is provided which comprisesa number of radio access network nodes, such as for example RNCs (RadioNetwork Controller), BSCs (Base State Controller), BTSs (BaseTransceiver Station, Node-B, UNCs (Unlicensed Network Controller),access points or wireless access gateways of for example wireless LANs,a number of first (core) network nodes serving communication of datasuch as for example SGSNs, MSCs (Mobile Switching Centers), PDGs (PacketData Gateways) or intermediate interworking gateways to for example aWLAN, a number of second core network nodes comprising gateway corenetwork nodes, for example GGSNs, acting as gateways to external orthird party controlled data communication networks and/or serviceproviders, whereby location related information of one or more mobileuser stations, for example mobile stations or user equipment, or moregenerally any mobile user station, obtained from the radio networkaccess nodes, is provided from a first (core) network node to a secondcore network node. According to the inventive concept, location relatedinformation is provided in one or more dedicated information elementsadded to existing communication of messages between said first (core)network node and said second core network node. The core network maycomprise 3G system such as an UMTS or a GPRS/GSM, with an access networksuch as UTRAN, GERAN with access network nodes, or an Unlicensed MobileAccess Network (UMA).

In one implementation location related information about one or moremobile user stations is provided from radio access network control nodesto the first (core) network node automatically or according to a knownprocedure. The location related information may also be provided, forone or more user stations, upon request by the first (core) networknode, which then may indicate for which particular mobile userstation(s) location related information is to be provided and even moreparticularly when or under which circumstances, e.g. for mobile userstations fulfilling certain criteria.

Particularly, a request from a first (core) network node or some othernode can be defined so as to refer to one or more specific mobile userstations. Even more particularly the request can be defined so as torefer to one or more mobile user stations fulfilling one or more givencriteria.

Particularly the location related information comprises informationabout the actual geographical location of a number of mobile userstations on a given level, e.g. cell level, RA (Routing Area) level,sub-cell level or service area level. The location related informationmay also or additionally comprise information about the time zone inwhich a mobile user station currently is located, preferably for mobileuser stations for which a change of time zone is plausible, i.e. whichare located there where change of time zone can be expected to occur. Inone particular embodiment the first (core) network node uses theLocation Report Control procedure to request location relatedinformation of a given mobile user station. However, the locationrelated information may also be requested in other manners.

The dedicated information element or elements is/are, in a mostadvantageous implementation, added to or included in the user planetraffic messages, i.e. to the payload sent from a first core network toa second core network node for the mobile station or stations concerned,or even all. In another implementation the dedicated informationelement(s) is/are added the user plane messages concerning such mobileuser stations for which the first core node has requested locationrelated information only.

In another embodiment the dedicated information element or elementsis/are added to existing messages comprising update PDP context requestsor similar from a first (core) network node to a second core networknode for all mobile user stations handled by said first core networknode or for those mobile user stations only for which the first corenetwork nodes has requested location related information.

Also other existing messaging could be used for adding the informationelement(s) containing location related information.

In one particular implementation the location related informationcomprises charging related information such as for example CGI/SAIinformation. Particularly means are provided for adaptive locationinformation provisioning to a second core network node from the first(core) network node.

Said means particularly comprises a client in the second core networknode. Even more particularly said client comprises an LCS (LocationServices) Client for requesting and collecting differentiated locationrelated information.

Therefore also a (core) network node as initially referred to isprovided which comprises means for establishing for which mobile userstations location related information is to be collected from the accessnetwork over which said mobile user stations are connected to said corenetwork, and means for collecting and means for storing said locationrelated information and means for providing location related informationto a second core network node acting as a gateway to external or thirdparty controlled communication systems or service providers. Said meansfor establishing, collecting and providing location related informationmay consist of common control means, or may be constituted of different,separate, cooperating or intercommunicating means.

Particularly the first (core) network node comprises an SGSN, a nodeacting as a gateway to a wireless access network, particularly a packetdata gateway, PDG, or any other corresponding node.

Even more particularly the node comprises means for providing saidlocation related information in one or more dedicated informationelements which may be the same means as the means for providing thelocation related information to a second core network node, or meansseparate there from. Said means for providing the location relatedinformation particularly comprises means for adding said informationelement to all payload traffic, i.e. all messages sent on the user planeof the established mobile user stations, e.g. using the GTP-U tunnel.Particularly said information is added to all traffical messages sentfrom mobile user stations for which the core network node has requestedLocation Report Control or for which a core network node (or any othernode or means) has requested location related information in any otherway, or more generally, for which location related information is to beprovided.

The core network node even more particularly comprises (control) means,in an alternative embodiment, for adding said information element orelements to messages sent to the second core network node when thelocation related information has changed for the mobile user station,e.g. when the mobile user station has changed geographical area, servicearea, cell and/or time zone. Said messages particularly comprise socalled Update PDP Context Requests.

The invention also suggests a core network node for a communicationssystem supporting communication of packet data which acts as a gatewaynode to external or third party controlled communications system orservice providers, which comprises means for receiving and collectinglocation related information for mobile user stations from a first corenetwork node, as discussed above. Said means comprises control meansfor, based on specified criteria, enabling adaptive collection oflocation related information for mobile user stations for which thespecified criteria are met, and for enabling adaptive reporting of suchlocation related information to external or third party controlled datacommunications systems or service providers. Said node particularlycomprises a GGSN. Said criteria are particularly mobile user stationlocation related, i.e. they may relate to the geographical location ofthe mobile user station, which then determines whether from thatparticular user station, where it is located, location relatedinformation is needed when it e.g. moves to another cell or to anotherservice area or to another time zone. The collected location relatedinformation particularly comprises geographical location information andsaid control means particularly comprises a LCS client allowing adaptivecollection of location related information on a per mobile user stationbasis. Particularly means are provided for transferring said locationrelated information to a GMLC (Gateway Mobile Location Center). It mayhowever be any kind of node or center having a functionality similar tothat of a gateway mobile location center. Particularly means areprovided for transferring said location related information to a GMLCallowing for, for example, adaptive location based service provisioningor adaptive location based charging.

Converting means for converting collected location related informationto another format, particularly to a format understandable to the thirdparty controlled data communication system or service provider may beprovided in the first (core) network node, in the second core networknode, e.g. a GGSN, according to different implementations.

The invention therefore also discloses a method as initially referredto, which comprises the steps of; establishing at least for which userstations location related information is to be collected in a first(core) network node; collecting said location information for saidmobile user stations; storing said location related information instoring means in or associated with said first (core) network node;arranging said location related information in dedicated informationelements; and adding said information elements to messages sentindependently of said information element(s) from said first (core)network node to the second core network node. That the messages are sentindependently of said information element means that already existingmessaging between first core network node and the second core networknode is used for transfer of said information element(s). The dedicatedinformation element may be added to all traffical packets sent in theuser plane for the concerned mobile user stations or it mayalternatively be added to other messages, e.g. in the control plane,such as Update PDP Context Requests. In an advantageous implementationit additionally comprises the step of converting, in said first or saidsecond core network node, said location related information to a formatunderstandable to users of said third party controlled datacommunications network or external service providers or more general toany desired format unless it is already in a desired format.

Most particularly the method comprises the step of; adaptively reportinglocation related information such as location information, time zoneinformation etc. to allow for location dependent rating or serviceprovisioning on a per mobile user station basis. The locationinformation may be on different levels, e.g. on cell level, service arealevel or any other appropriate level. It may particularly comprisegeographical coordinates or it may be converted to such. The locationinformation may also alternatively or additionally comprise time zoneinformation.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will in the following be further described, in anon-limiting manner, and with reference to the accompanying drawings, inwhich:

FIG. 1 is a schematical block diagram of a part of an UMTS or GSM/GPRSarchitecture in which location related information is provided to a GGSNaccording to a first implementation of the inventive concept,

FIG. 2 is a figure similar to FIG. 1 illustrating provisioning oflocation related information according to a second implementation of theinventive concept,

FIG. 3 is a schematical block diagram of a system in which the accessnetwork comprises an unlicensed mobile access network and to which theinventive concept can be implemented,

FIG. 4 is a schematical block diagram of a system in which the accessnetwork comprises a WLAN,

FIG. 5 is a schematical block diagram of a system of an alternativeimplementation in which the access network comprises a WLAN,

FIG. 6 illustrates a traffical packet with the dedicated informationelement for provisioning of the location related information to a GGSNaccording to one embodiment of the invention,

FIG. 7 is a sequence diagram illustrating the inter SGSN routing areaupdate procedure as adapted for location related informationprovisioning according to another embodiment of the invention,

FIG. 8 illustrates an example of a user location information element,indicating CGI/SAI, that can be used,

FIG. 9 illustrates geographic location type values and the meaningsthereof for an embodiment using a location information element as inFIG. 8,

FIG. 10 illustrates geographic location fields for CGI for the FIG. 8embodiment according to one implementation,

FIG. 11 illustrates an example of a geographic location field for SAIfor the embodiment of FIG. 8 according to one implementation,

FIG. 12A illustrates one example on a location related informationelement comprising an MS time zone element,

FIG. 12B illustrates possible values for the daylight saving time fieldand the meaning thereof,

FIG. 13 illustrates an embodiment in which an LCS client is introducedin GGSN,

FIG. 14 schematically illustrates a part of a communication system withan LCS client in GGSN,

FIG. 15 shows an LCS architecture with an LCS client in a GGSN,

FIG. 16 is a schematical flow diagram showing location relatedinformation provisioning to a GGSN according to one exemplaryembodiment, and

FIG. 17 is a sequence diagram illustrating flow based charging in GGSNwith differentiated rating depending on location.

DETAILED DESCRIPTION OF THE INVENTION

The present invention generally relates to providing a core networknode, generally denoted a second network core (CN) node, particularly aGGSN, with location related information for one or more mobile userstations, e.g. mobile user stations for which location relatedinformation has been requested, for all mobile user stations or formobile user stations fulfilling one or more given criteria e.g. as faras location is concerned. The location related information can be ofdifferent kinds as will be more thoroughly discussed below, for examplepure location information, e.g. indicating geographical area, ondifferent levels or in different forms, for example on cell level,service area level or geographical coordinates or any other form tospecify an area, but it may also comprise information about in whichtime zone a mobile user station currently is located. It may also bedifferent or on different levels etc. for different mobile userstations. The inventive concept is applicable to 3G (Third GenerationPartnership Project) systems, e.g. UMTS based on WCDMA (Wideband CodeDivision Multiple Access) technologies as well as to other systems andto other access networks, for example WLAN (Wireless Local Area Network)inter working with 3G and Unlicensed Mobile Access (UMA) etc.

FIG. 1 is a schematical block diagram of a first example of animplementation to a 3G UMTS system built on the WCDMA technologyarchitecture. In a simplified manner is illustrated a routing area RAcomprising three cells, cell A, cell B, cell C in which a mobile userstation or a user equipment MS is moving around, in this particular caseit is supposed that it moves from cell A to cell B. Cell A is here via abase station BS 1A₁, controlled by RNC (Radio Network Controller) or BSC(Base Station Controller) 2A₁ whereas cell B via base station BS 1B₁ andcell C via base station BS 1C₁ are controlled by RNC/BSC 2B₁. RNC/BSC2A₁ here connects to the core network by means of first CN node SGSN 13A₁, whereas RNC/BSC 2B₁ is connected to first CN node SGSN 2 3B₁. BothSGSN 1 3A₁ and SGSN 2 3B₁ communicate with second CN node GGSN (GatewayGPRS Support Node) 4 ₁. It should be clear that this is merely asimplified illustration and the inventive concept is also among otherapplicable to pooling concepts as for example described in“Communication system supporting wireless communication of packet dataand method and arrangement relating thereto” filed by the same applicanton Oct. 13, 2000 and which herewith is incorporated herein by reference.

It is in this embodiment supposed that MS moves from cell A to cell B.It is in this particular case supposed that the SGSN has requested thatlocation related information be provided for MS. When MS moves from cellA to cell B, information as to that is provided from BS 1B₁ to RNC/BSC2B₁, which hereupon provides such location related information to SGSN 23B₁. In FIG. 1 control means are illustrated in SGSN 1 and SGSN 2respectively which here are supposed to handle establishment of forwhich mobile stations location related information should be providedand to handle collection of such information from the RNC/BSC inquestion and further to provide for storing of such location relatedinformation in a database DB, for example an existing database in theSGSN holding location information for all subscribers, e.g. the MMcontext data database (Mobility Management database) or in a specificdatabase or a database associated with SGSN. The control means are alsoresponsible for making sure that the location related information isprovided to GGSN, i.e. the relevant location related information is thusfetched from the database when sending of a message (e.g. a trafficalpacket in the user plane) to SGSN is due. In the particular embodimentillustrated in FIG. 1, it is supposed that the control means also areresponsible for providing the location related information in a new(dedicated) information element (IE) which is sent in the User Plane,i.e. over GTP-U (GPRS Tunneling Protocol-User plane). The relevantinformation element(s) is/are thus added to traffic payload sent from MSvia SGSN 2 to GGSN and hence added to all messages for the particularuser, in this case MS. The SGSN control means are used to add thededicated information element(s) to all messages particularly byextending the GPP-U header with the location related information. In analternative, advantageous, implementation only one (or a limited numberof) GTP-U packet is extended with location information each time the UEchanges e.g. cell or RA. This is advantageous in that it eliminatesredundant information sent to GGSN and in that it minimizes processingtime in GGSN to handle the embedded location information in the GTP-Upacket. Even if there is a slight risk that a single GTP-U packet getslost, the benefit should outweight this risk.

In FIG. 1 it is further illustrated that converting means are providedin GGSN 4 ₁. The converting means are used to convert the locationrelated information of the dedicated information element IE to a formatunderstandable to a third party communication system connected to GGSN,for example Internet, or to external service providers etc. Theseconverting means are not necessary for the functioning of the inventiveconcept but generally it is desirable to be able to provide the locationrelated information in an appropriate form to allow for example forservice providers to offer services etc. The converting means could alsohave been provided in SGSN 2 (and SGSN 1). When the interface betweenRNC/BSC and SGSN in Iu (i.e. not Gb), GTP-U may be used to convey thelocation information in the same manner as on the Gn-interface. Whenusing GTP-U the GGSN will only receive updates of location of UEs whenthey are active. That is, when the user is using some PS based service.Many times when a user is moving, he is not using any PS service at all,and hence the GGSN will fail to be updated. This problem can be solvedin for example the following way: Every time an SGSN or RNC/BSC becomesaware that a UE has changed Cell (or RA), it updates its DB with the newlocation and searches for any GTP-U communication of the UE to conveyits location to the next CN node. If no GTP-U communication (packets)are found within a certain time (a timer T1 may e.g. be set), the nodegenerates a GTP-U packet itself “on behalf of” the UE and forwards thisto the next CN node. The location information is inserted in thisgenerated GTP-U packet. The IP packet which is encapsulated in the GTP-Upacket may be constructed in such a way that it is discarded by theGGSN. It may for example be a PING message which GGSN will not answer,or with a faulty destination address e.g. 0.0.0.0 that the GGSN willhave to discard. This generated “dummy” packet will convey the locationinformation to the GGSN at a very low cost, and still use the sameconcept as if GTP-U communication is present.

The timer can be set to a reasonable high value, e.g. minutes, to avoidfrequent updates e.g. for UEs which are moving fast on a highway andquickly moving between cells. Depending on how the location informationis used by receiving applications, UEs only staying a very short time ina cell may not be of interest. The timer T1 could hence be reset everytime the UE moves to a new cell or RA.

It should be clear that in this embodiment the information element couldalternatively have been included in an Update PDP Context Request assent from SGSN 2 to GGSN 4 ₁ for example whenever MS changes thegeographical area, which is detected via SGSN which then sends theupdated location related information to GGSN in a new informationelement added to an Update PDP Context Request instead. However, thefirst solution relating to sending information elements in the userplane minimizes the amount of signalling which is extremelyadvantageous.

FIG. 2 shows another implementation of the inventive concept. It is alsohere supposed that routing area RA comprises three cells, cell A, cellB, cell C. Here mobile user station MS moves from cell B to cell C andBS 1A₂ covers cell A, BS 1B₂ covers cell B, whereas BS 1C₂ covers cellC. BS 1A₂ is controlled by RNC/BSC 2A₂ whereas BSs 1B₂, 1C₂ arecontrolled by RNC/BSC 2B₂. RNC/BSC 2A₂ is here connected to first CNnode SGSN 1 3A₂ whereas RNC/BSC 2B₂ is connected to first CN node SGSN 23B₂. SGSN 1 and SGSN 2 communicate with GGSN 4 ₂, i.e. the second CNnode. Like in the preceding embodiment, described with reference to FIG.1, it is supposed that the first CN nodes SGSN 1 and SGSN 2 comprisecontrol means and a database respectively. However, in this embodimentit is illustrated that converting means are provided in SGSN 1 and SGSN2 respectively. In this particular implementation it is also supposedthat GGSN 4 ₂ comprises an LCS client (Location Services). The LCSclient particularly allows collection of location information requiredfor e.g. rating to be properly differentiated based on location. The LCSclient is defined in 3GPP TS 23.271, section 6.3.2, which herewith isincorporated herein by reference. The LCS client can also be responsiblefor collecting location related information in the form of time zoneinformation etc. The inclusion of an LCS client is however not necessaryfor the basic concept of the present invention but it merely disclosesan advantageous implementation, (and requires a GMLC as will beexplained below). Moreover, an LCS client as will be more thoroughlydescribed below with reference to FIGS. 13, 14 and 15 mightalternatively be included in a GGSN without the implementation of thededicated information element sent using already existing messaging forprovisioning of location related information to a GGSN, i.e. relying onthe GMLC (cf. e.g. FIGS. 13-15).

As referred to with reference to FIG. 1 also the converting means arenot necessary for the functioning of the inventive concept, but if suchare provided, they may, as in FIG. 1, be included in the GGSN instead.

Thus, in FIG. 2 it is supposed that BS 1C₂ provides location relatedinformation to RNC/BSC 2B₂ which in turn forwards said location relatedinformation concerning MS to the control means of SGSN 2 3B₂, which forexample explicitly may have requested location related information forMS. In other aspects the functioning is similar to that described withreference to FIG. 1 and SGSN 2 provides the location related informationto, here, the LCS client of GGSN 4 ₂. Also without inclusion of this LCSclient in GGSN, the location related information would of course beprovided to GGSN 4 ₂. This transfer is via GMLC, which provides theinformation to the LCS client in the GGSN. The GMLC may process and/orconvert the location information as required to meet the demands fromthe LCS client's client (e.g. the charging framework). The GMLC may usethe SGSN or MSC to collect location information, and uses the options ofthe Lg interface to optimize the data collection. The GMLC may evencollect GPS data from an MS that supports GPS positioning. In theillustrated embodiment a PDP Context Update Request is used as existingmessaging, and to which a dedicated information element is added asdiscussed with reference to FIG. 1. Of course, alternatively theinformation element might have been added to the user (traffic) planemessages, i.e. the user packets from MS.

FIG. 3 shows an embodiment in which the inventive concept is used in asystem with an Unlicensed Mobile Access network (UMA). The functioningis similar to that described above with the reference to the FIGS. 1 and2 with the difference that the access network comprises an UMA with anaccess point 1C controlled by an Unlicensed Network Controller UNC 2Cwhich functions substantially in the same manner as an RNC. The UNC 2Ccommunicates with a first CN node SGSN 3 3C over the Gb/Iu interface andhere with an MSC over the A/Iu interface. The MSC in turn communicateswith a RAN for circuit switched communication. Also RAN communicateswith the first CN node SGSN 3 3C. As the MS moves, location relatedinformation is provided to the control means of SGSN 3 3C as describedwith reference to for example FIGS. 1 and 2. SGSN 3 3C stores thelocation related information in a database DB for forwarding to thesecond core node GGSN 1 4 ₂ in a dedicated information element IE. It isof course also here possible to either extend the traffic payloadmessages with the location related information dedicated informationelement in all traffical packets from the MS for which location relatedinformation should be provided to e.g. GGSN 1 4 ₂ or alternatively toadd one or more dedicated information elements to Update PDP ContextRequests. Assuming that the Gb/Iu or A/Iu supports location basedservices (LCS), i.e. having an LCS client in the GGSN, is possible hereas well. In order to indicate that both methods can be used, thetransfer to GGSN 1 4 ₂ merely is indicated as location related IE in thefigure. In other aspects the functioning is similar to that describedabove. Converting means may optionally be provided in SGSN 3 3C or GGSN2 4 ₂.

FIG. 4 describes still another an embodiment in which the inventiveconcept is implemented in a system or an architecture in which a WLANinterworks with a 3G system. In this embodiment it is illustrated howlocation related information about an MS is provided from a WLAN AP 1Dto a wireless local area network access gateway WAG 2D which forwardsthe information to a packet data gateway PDG 3D which, even if itactually does not belong to the core network, here is referred to as afirst (CN) node, similar to an SGSN, which therefore contains thecontrol means and the database as discussed above according to FIGS. 1-3with reference to SGSNs. The PDG then transfers the location relateddedicated IEs to the second CN node GGSN 43. Also in this case thededicated information element or elements IE could be added to alltraffical packets from the concerned MS, or the dedicated IE could beadded to PDP Context Update Requests from PDG 3D to GGSN 43. Convertingmeans (not shown) may optionally be included in PDG 3D and/or GGSN 43.

FIG. 5 shows still another example of an implementation in which a WLANinterworks with a 3G system. In this case, however, it is supposed thatan interworking gateway node 2E communicates with an SGSN, a first CNnode 3E with control means and database as discussed above which thusforwards location related information either in the user plane includedin all traffical packets from MS or as an additional information elementadded to an Update PDP Context Request sent from SGSN 3E to GGSN 44. Thelocation related information about the MS is thus forwarded from WLAN AP1E to the interworking gateway node 2E. In all the embodiments describedwith reference to FIGS. 3-5, any converting means could optionally beprovided either in SGSN or PDG or in GGSN.

FIG. 6 shows a dedicated location related information element IEaccording to the invention to be sent in the user plane, i.e. overGTP-U. This means that an SGSN (or a PDG or similar) includes thisinformation for all messages towards a GGSN from a particular user ifthe SGSN has requested the provisioning of location related informationas far as that user is concerned, particularly if the SGSN has requestedlocation reporting control for that user. In an alternative embodimentit could be done for all users. More generally it can be controlled inany manner for which users reporting should apply and SGSN does notnecessarily have to explicitly request information. Requests could alsooriginate from other nodes or external means etc., or it can be seen asa request if an MS fulfills some predefined criteria, i.e. is located inan area, in which provisioning of location related information is wantedfor whatever reason.

This means that SGSN to the GTP-U header adds an extension headerincluding e.g. user location, particularly a new CGI information elementin all (or one or a limited number only) user plane packets towards theGGSN in one particular embodiment. This gives GGSN accurate locationinformation since particularly, according to one embodiment every cellchange will be visible to the GGSN, in case location information isrequested on cell level. It should be clear that different kinds oflocation related information can be requested and provided to GGSN, ondifferent levels, in different forms or for example as time zoneinformation. This method enables very high accuracy and minimizes thesignalling load as compared to the alternative in which dedicatedinformation elements are added to Update PDP Context Requests.

Packets from an MS in the direction towards the external network arehence encapsulated and tunneled from the SGSN to the GGSN by the GPRSTunnelling protocol GTP. In this particular embodiment an extensionheader, including a new, also called dedicated, information element,which in one implementation is a so called CGI information element, isadded to the GTP header. This is done in the user plane, GTP-U, andhence the SGSN includes the location related information in all packetstowards the GGSN as mentioned above. As can see from the figure a GTP-Upacket comprises a GTP-U header as is conventional, but in additionthereto it is provided with an extension header including for example auser location information element. In a more particular embodiment itmay also comprise an MS time zone information element. The packet alsocomprises the user payload, i.e. the user packet coming from the MS.Examples on user location information elements and time zone informationelements will be given with reference to FIGS. 8,9,10,11,12A,12B. Ofcourse also other types of information elements are possible, theremight be more information elements and the structure may be differentand therefore these examples should not be seen in a limitativeperspective.

FIG. 7 is a sequence diagram illustrating an embodiment in which thededicated information element is added to an Update PDP Context Request.Whenever, for example, a mobile station or a user equipment (UE) haschanged geographical area, this will be detected by the SGSN (or PDG)which sends the updated coordinates to the GGSN in a dedicated (new)information element which is added to an Update PDP Context Request. theInter SGSN Routing Area Update procedure is described in 3GPP TS 23.060,ch. 6.9.1.2.2. In the sequence diagram of FIG. 7, the dedicatedinformation element, particularly a CGI information element, is added tothe Update PDP Context Request message 6 sent from SGSN 2 to GGSN. Inother aspects the signalling sequence is similar to that described inthe above mentioned standard.

Thus, it is supposed that an MS sends a Routing Area Update Request to anew, here called a second SGSN 2, 1. SGSN 2 subsequently sends an SGSNContext Request to the old SGSN 1 to get MM (Mobility Management) andPDP Contexts for the MS, 2. SGSN 1 responds with an SGSN ContextResponse to SGSN 2, 2. Optionally security functions may be executed, 3.SGSN 2 then sends a SGSN Context Acknowledgement message to SGSN 1. Thismessage informs the first SGSN 1 that the second SGSN 2 is ready toreceive data packets belonging to the activated PDP Context, 4. SGSN 1duplicates buffered N-PDUs (Packet Data Units) and starts tunnellingthem to SGSN 2, 5. SGSN 2 then sends an Update PDP Context Request withthe new SGSN address, (address of SGSN 2) TEID, QoS negotiated, and userlocation related information of any kind, for example also includingmobile station time zone, to the concerned GGSN. The GGSNs then updatePDP Context Fields and return Update PDP Context Response to SGSN 2. Thelocation related information provides information for example about thegeographical location of a mobile station. It may also (or only) includetime zone information as to in which time zone the mobile stationcurrently resides, 6. Subsequently SGSN 2 informs the HLR about the SGSNchange by sending update location to HLR, 7, and HLR sends a cancellocation to SGSN 1, 8. The HLR then sends Insert Subscriber Data (IMSIInternational Mobile Subscriber Identity etc.) to SGSN 2 which validatesthe presence of the MS in the (new) RA etc., 9. The HLR subsequentlyacknowledges the Update Location by sending an Update LocationAcknowledgement (IMSI) to SGSN 2, 10. Subsequently SGSN 2 validates thepresence of the MS in the new RA, 11, and the MS acknowledges a newP-TMSI by returning a Routing Area Update complete message to SGSN 2.

In the case of a rejected routing area update operation, due to regionalsubscription or roaming restrictions, or because the SGSN cannotdetermine the HLR address to establish the locating updating dialogue,the new SGSN shall not construct an MM context. A reject shall bereturned to the MS with an appropriate cause. The MS does no re-attempta routing area update to that RA. The RAI value shall be deleted whenthe MS is powered up. If the new SGSN is unable to update the PDPcontext in one or more GGSNs, the new SGSN shall deactivate thecorresponding PDP contexts. This shall not cause the SGSN to reject therouting area update. The PDP Contexts shall be sent from old (second) tonew (first) SGSN in a prioritized order, i.e. the most important PDPContext first in the SGSN Context Response message. (The prioritizationmethod is implementation dependent, but should be based on the currentactivity). If the new SGSN is unable to support the same number ofactive PDP contexts as received from old (first) SGSN, the new (second)SGSN should use the prioritization sent by old SGSN as input whendeciding which PDP contexts to maintain active and which ones to delete.In any case, the new SGSN shall first update all contexts in one or moreGGSNs and then deactivate the context(s) that it cannot maintain. Thisshall not cause the SGSN to reject the routing area update. If a timerused in step 2 expires and no Cancel Location (IMSI) was received fromthe HLR, the old (first) SGSN stops forwarding N-PDUs to the new(second) SGSN. If the routing area update procedure fails a maximumallowable number of times, or if the SGSN returns a Routing Area UpdateReject (Cause) message, the MS shall enter IDLE state. The CAMELprocedure calls shall be performed, see referenced procedures in 3GPP TS23.078:

-   C1) CAMEL_GPRS_PDP_Context_Disconnection, CAMEL_GPRS_Detach and    CAMEL_PS_Notification.

They are called in the following order:

-   -   The CAMEL_GPRS_PDP_Context_Disconnection procedure is called        several times: once per PDP context. The procedure returns as        result “Continue”.    -   Then the CAMEL_GPRS_Detach procedure is called once. The        procedure returns as result “Continue”.    -   Then the CAMEL_PS_Notification procedure is called once. The        procedure return as result “Continue”.

-   C2) CAMEL_GPRS_Routing_Area_Update_Session and    CAMEL_PS_Notification.

They are called in the following order:

-   -   The CAMEL_GPRS_Routing_Area_Update_Session procedure is called.        The procedure returns as result “Continue”.    -   Then the CAMEL_PS_Notification procedure is called. The        procedure returns as result “Continue”.

-   C3) CAMEL_GPRS_Routing_Area_Update_Context.

This procedure is called several times: once per PDP context. It returnsas result “Continue”.

FIGS. 8,9,10,11 give examples on how a dedicated information element oruser location information can be defined. As referred to above the SGSNor for example a PDG provides this information to GGSN. FIG. 8particularly describes the user location information IE which in thiscase is used to indicate CGI/SAI (Cell Global Identifier/Service AreaIdentifier) of where the MS currently is located. The “GeographicLocation Type” field is used to convey whether or not location field isincluded, and if so, what type of location. The types of locations thatcan be conveyed in this particular implementation are defined in FIG. 9which shows a table with the geographic location type values and theirmeanings.

The “Geographic Location” field is used to convey the actual geographicinformation as indicated in the “Geographic Location Type” field. Thisfield shall not be present if the value of the “Geographic LocationType” field is 0. In the table of FIG. 9 is referred to 3GPP TS 23.003,sub-clause 4.3.1 and 3GPP TS 25.413, sub-clause 9.2.3.9 which herewithare incorporated herein by reference.

The location information is generally only of interest for the end pointnodes and intermediate nodes need not be able to comprehend the locationinformation. The GTP header is a header of variable length used forGTP-C (Control Plane) and GTP-U (User Plane) protocols. It among otherscomprises an always present field, Extension Header Flag, indicating thepresence of a meaningful value of the Next Extension Header Field.According to this embodiment of the present invention bits 8,7 of theNext Extension Header Type might be set to 1 0, indicating thatcomprehension of this extension header is required by the End PointReceiver but not by Intermediate Nodes, which are supposed to forwardthe whole field to the End Point. Alternatively it might be 0 0,indicating that comprehension is not required. Other alternatives arealso possible. This is described in 3GPP TS 29.060 v.6.5.0. However, itshould be clear that also entirely different implementations arepossible.

FIG. 10 illustrates the geographic location field for CGI. If only twodigits are included in the MNC, then bits 5 to 8 of octet 6 are coded as“1111”. The location area code consists of 2 octets and is found inoctet 8 and octet 9. Bit 8 of octet 8 is the most significant bit andbit 1 of octet 9 the least significant bit. The coding of the locationarea code is their responsibility of each administration. Coding usingfull hexadecimal representation shall be used. The cell identityconsists of two octets and is found in octet 10 and octet 11. Bit 8 ofoctet 10 is the most significant bit and bit 1 of octet 11 the leastsignificant bit. The coding of the cell identity is the responsibilityof each administration. Preferably full hexadecimal representation isused.

FIG. 11 finally describes as a table describing the geographic locationfield for SAI.

If only two digits are included in the MNC, then bits 5-8 of octet 6 arecoded as “1111”. The location area code consists of two octets and it isfound in octet 8 and octet 9. Bit 8 of octet 8 is the most significantbit, and bit 1 of octet 9 is the least significant bit. The coding ofthe location area should be the responsibility of a respectiveadministration. Again coding using full hexadecimal representationshould be used, cf. 3GPP TS 24.008 which herewith is incorporated hereinby reference.

The service area code consists of 2 octets and it is found in octets 10and 11. Bit 8 of octet 10 is the most significant whereas bit 1 of octet11 is the least significant bit. SAC is operator defined, cf. 3GPP TS23.003 section 12.5 which herewith is incorporated herein by reference.

As referred to above the time zone information element may additionallyor alternatively be included, or together with any other locationrelated information; any combination is in principle possible. The timezone information element can with advantage be used together with thelocation information to offer better and more accurate charging andlocation based services. The MS time zone information element is used toindicate the offset between universal time and local time in the stepsof 15 minutes of where the MS currently resides. The time zone field inone embodiment uses the same form at as the time zone informationelement discussed above with reference to FIG. 8, cf. 3GPP TS 24.008,and it is shown in FIG. 12A.

FIG. 12B gives an example on possible values for the daylight savingtime field and meanings thereof. It should be clear that the examples anlocation related information elements and time zone elements merely aregiven for exemplary reasons, and the invention is by know means limitedto the use of these specific elements.

With the location information and the time zone information in the GGSN,more accurate charging based on location and time of day gets possible.It also gives a network operator or an external service providerprovided with this information, the opportunity to develop locationbased applications, particularly with a better accuracy which adds valuefor the operators as well as for the customers of the operator.

FIG. 13 shows a particular embodiment allowing for example operators toapply different rating depending on the location of a MS/UE while theappropriate location information is available in the GGSN and, inaddition thereto, in a timely manner. According to the shown solutionlocation reporting granularity can be different for different MSs/UEs aswell as the triggering of recording can be different.

This is for example advantageous if there is a “free of charge” ratingin one cell, whereas a common rating applies in all other locations. Thelocation tracking then does not need to be so accurate when the MS/UE islocated outside that particular routing area which contains the “free ofcharge cell”. According to the embodiment discussed with reference toFIGS. 13-15, e.g. Flow Based Rating in GGSN is extended withdifferentiated rating (or other service provisioning) depending onlocation. The characteristics of the different areas (routing areas,service areas, cells etc.) may result in different needs for thecollection of location information i.e. on which level (service arealevel, RA level, cell level etc.) and/or on frequency or timing forcollecting the information.

3GPP TS 23.271 (with particular reference to section 6.3.2.) specifies aLocation Services (LCS). According to the present invention such an LCSclient 9 is introduced in GGSN 4 ₅. This provides for the possibility tocollect location related information, particularly over the Leinterface, which is adapted to the actual needs e.g. for ratingpurposes, most particularly on a per MS/UE basis. Thus, the inclusion ofthe LCS client 9 in GGSN 4 ₅ allows for collection of location relatedinformation in a manner appropriate for rating to be properlydifferentiated based on location. Both the accuracy and frequency forthe data collection can be adapted to the needs for rating. It issufficient if either the CS or PS access network supports LCS in orderto make use of this alternative. The architecture for Flow BasedCharging is defined in 3GPP TS 23.125, which herewith is incorporatedherein by reference.

The architecture according to the invention comprises an LCS client 9 inthe Traffic Plane Function TPF 8 in GGSN 4 ₅ for collection of locationinformation, particularly for rating purposes. The LCS client 9 in theTPF 8 subscribes to location information from the GMLC when the tarifffor a user, according to Flow Based Charging, depends on the location ofthe mobile user station, e.g. the UE. In an advantageous embodiment thestandardized Le interface Le/LIF-MLP as specified by 3GPP Rel. 6, 29.198is used towards the GMLC.

In a particular implementation the LCS client issues a Location DeferredRequest with event triggers for a mobile user stationentering/leaving/camping in interesting areas. Examples on such eventtriggers are PLMN id, country code, time zone or other location relatedevents. The time zone trigger is particularly an extension to Le. Inother implementations, or additionally, other pre-defined triggerschemes or trigger events may be developed and implemented in the GMLCon a per need basis.

In advantageous implementations the LCS client 9 includes optimizations,such that location related information is collected only for subscriberswith e.g. a rating depending on the location of the mobile user stationlocation, and/or the accuracy and a timing of the location relatedinformation is adapted to the need for performing rating (or providingsome kind of services). Examples hereon are when a mobile user stationroams to another operator there is a single rate that differs from theHPLMN rate, which does not require exact location information, it ise.g. sufficient with MLC/MNC. Another example relates to the case whenthere e.g. is a low rate when the mobile user station is located in the“home cell”, but otherwise a higher rate. Then accurate locationinformation is collected in that routing area (RA) where the “home cell”is located. At other locations, or in other RAs in the HPLMN merely atracking of RA changes is necessitated or sufficient. The GMLC collectslocation information from SGSN and/or MSC, cf. FIG. 15 below.

FIG. 14 schematically illustrates a block diagram in which an LCS client5 is provided in a second CN node, GGSN 4F, or more specifically in theTraffic Plane Function thereof. The LCS client then subscribes forlocation information from a GMLC 6 over the Le interface as discussedabove. Location information about UE is provided over RAN 2F to SGSN 3F(or to an MSC where the UE is attached) which provides information toGMLC 6 over the Lg interface. (Location related information may betransferred from SGSN 3F to GGSN 4F using existing messaging asdiscussed earlier in the application, i.e. as dedicated IEs added totraffical packets over GTP-U or dedicated IEs added to e.g. Update PDPContext Requests. The initial location information, provided in thecreate PDP Context Request may help the LCS client to issue a tailoredsubscription for location reports from the GMLC.) However, the conceptwith an LCS client in the GGSN for collecting location information incommunication with a GMLC is also applicable when location informationis provided in other or conventional manners to GGSN.

It is an advantage of the implementation as described with reference toFIGS. 13,14,15, that location information for mobile user stations witha session established can be collected in the GGSN e.g. for ratingpurposes. Particularly the collection of location information can berestricted to mobile user stations where the rating depends on location.Further, the collection of location information may be optimized permobile user station with an appropriate accuracy to perform rating orother location dependent services. Most advantageously the collection oflocation information may utilize the circuit switched (CS) part over anMSC of the network to collect location information to the GMLC as canalso be seen in FIG. 15. This is relevant in case the SGSN does notsupport LCS. Basically this means that the implementation of thisembodiment does not depend on an SGSN supporting LCS, if it does not,the MSC can be used instead for the same purposes, which is extremelyadvantageous.

In one embodiment location information is expressed in terms that do notdepend on RAN e.g. GPS (Global Positioning System) information collectedby the GMLC. Still further the GMLC may include specialized logic toprovide information tailored for the TPF needs, e.g. to provide timezone information for a mobile user station.

Thus, the embodiment described with reference to FIGS. 13-15 combinesthe concept of Flow Based Charging and a possibility to implement ratingthat depends on user location without causing unnecessary signalling formobile user stations where the location information actually isirrelevant or not needed for the rating or whatever purpose that is tobe provided or offered.

The collection of location information is advantageously made adaptivesuch that unnecessarily frequent or accurate information collection isavoided, which results in benefits as far as signalling and performanceis concerned.

This is particularly of importance when not already existing messagingis used for providing location related information, but it stillprovides a high variety and flexibility also for other purposes thanreducing unnecessary signalling.

In FIG. 15 can be seen how mobile user stations UE are connected to aGERAN 2G and an UTRAN 2H respectively. The GERAN 2G is connected overthe A-interface to a 2G-MSC 3G, and over the Gb-interface to a 2G-SGSN3G₂. Further it is connected to a 3G-SGSN 3G₃ and an MSC-server 3G₄ overthe Iu-interface. UTRAN 2H is connected to the 3G-SGSN 3G₃ and theMSC-server 3G₄ over the Iu-interface. All core network nodes, i.e. MSC,SGSN and MSC-server are connected over the Lg-interface with the GMLC61, which communicates with the LCS client in GGSN 4G over theLe-interfaces as discussed above.

It should be clear that this merely illustrates one particular,advantageous, implementation of a second aspect of the presentinvention.

FIG. 16 is a flow diagram showing one embodiment of the presentinvention in which dedicated information elements are added to all theuser packets, from a mobile user station for which location relatedinformation is to be provided to e.g. a GGSN. Hence, it is firstestablished in a 1^(st) (core) network node, e.g. an SGSN (or a PDG incase of a WLAN access network being used) for which MS/UE(s) locationrelated information is to be collected, 100. Location relatedinformation may have been requested from a GGSN, external networks;specific mobile user stations may pointed out, or mobile user stationsmeeting given criteria may be indirectly indicated, or it may concernall mobile user stations handled by e.g. the SGSN. The 1^(st) (core)network node, in the following denoted SGSN for reasons of simplicity,then establishes which type/level of location related information thatis to be collected, or that is of interest, in the latter case the SGSNonly storing or sorting the relevant information, e.g. locationinformation on cell-level or service area etc., 101.

Once this is done, SGSN requests such information, or generally locationrelated information, from the radio access network, particularly controlnodes such as RAN, RNC, UNC etc. as discussed earlier in theapplication, 102. The requested location related information is thencollected in SGSN, 103. The collected location related information is,in SGSN, arranged in new, also called dedicated, information element(s)IE, 104.

The collected information, the IEs, are stored in storing means in SGSN,e.g. in a DB, particularly an existing subscriber database, e.g. the MMDB, even if also other alternatives are possible. The location relatedinformation is of course sorted and associated with the appropriatemobile user stations, 105.

Subsequently, when a user packet arrives in SGSN from an establishedmobile user station, this is detected, 106, the corresponding IE fetchedfrom the DB, and the user packet is encapsulated in SGSN in a GTP-Upacket and the fetched IE is added to the GTP-U header of the userpacket, 107. The encapsulated user packet with the dedicated IE is thentunneled by GTP-U to the GGSN, 108. This is done for all user packetsfrom all established mobile user stations.

It should be clear that one or more dedicated IEs can be added dependingon how the information is arranged and in which location relatedinformation that is requested. It may e.g. be one IE for user locationand one for time zone information etc.

The principle remains the same if the IE(s) are added to Update PDPContext Requests from e.g. SGSN to GGSN, but then the information isprovided in the signalling plane.

As referred to earlier in the application an LCS client orcorrespondingly may be arranged in GGSN, and GGSN may use/forward thereceived location related information in many different manners, e.g. toexternal service providers.

FIG. 17 is a sequence diagram describing the procedure when flow basedcharging in GGSN is extended or provided with differentiated ratingdepending on location, when an LCS client is provided in GGSN (cf. FIGS.13-15) for collecting location information for rating purposes.

1,2 relates to activation and creation of a PDP Context Request, in aconventional manner. A request for charging rules 3, is then sent fromGGSN to CRF (Charging Rules Function), which provides the charging rulesto GGSN, 4. Then, according to the invention, a triggered LocationReporting Request is sent from GGSN to GMLC, 5, which responds with amessage Provide Subscriber Location, 6. This is acknowledged by SGSN toGMLC, 7. Then a Triggered Location Reporting Answer message is sent fromGMLC to GGSN, 8. A Credit Request may then be sent from GGSN to CCS(On-line Charging System), 9, which responds with a Credit Response, 10.A Create PDP Context Response, 11, is then provided from GGSN to SGSN,11, which sends an Activate PDP Context Accept to the MS, 12. 13indicates a Triggered Location Report from GMLC to GGSN, which is novellike messages 5-8.

Later it is supposed that a Deactivate PDP Context Request is sent fromMS to SGSN, 14, which thereupon sends a Delete PDP Context Request toGGSN, 15. GGSN then sends an Indication of Bearer Termination to CRF,16, which sends a message Provision of Charging Rules to GGSN. After thesending of a message Final Remaining Credit Report to CCS, 18, and theresponse to that, 19, to GGSN, 19, a Triggered Location Reporting StopRequest, 20, is sent from GGSN to GMLC. GMLC returns an answer to GGSN,21. These messages 20, 21 are also novel and terminate the subscriptionto location reporting.

Finally follows a Delete PDP Context Response, 22, and a Deactivate PDPContext Accept, 23, in a conventional manner. It should be clear thatthis merely illustrates one specific implementation.

The location related information may be used and taken advantage of inmany different manners, e.g. for rating or charging purposes, but alsofor many other purposes, e.g. for providing services to relevant mobileuser stations in a relevant area or location, e.g. for warning fortraffic hazards in particular locations or to offer relevant services.

It should be clear that the invention by no means is limited to thespecifically illustrated embodiments, but that it can be varied in anumber of ways within the scope of the appended claims.

1-38. (canceled)
 39. A system for providing a core network node withlocation related information about one or more mobile user stationsaccessing the core network over an access network, comprising a numberof radio access network nodes (RAN;RNC;BSC;UNC;AP;BTS; Node-B), a numberof first network nodes or core network nodes serving communication ofdata (SGSN;MSC;PDG), a number of second core network nodes comprisinggateway core network nodes (GGSN) acting as gateways to external orthird party controlled data communication networks and/or serviceproviders, that location related information of one or more mobile userstations obtained from the radio network access nodes is provided from afirst network node or core network node to a second core network node,characterized in that said location related information is provided inone or more dedicated information elements added to existingcommunication of user plane traffic messages between said first corenetwork node and said second core network node, i.e. the payload.
 40. Asystem according to claim 39, characterized in that the second corenetwork node comprises a GGSN (Gateway GPRS Support Node) and in thatthe first core network node comprises a SGSN (Serving GPRS SupportNode).
 41. A system according to claim 39, characterized in that theaccess network is a WLAN, the radio network access nodes comprisingaccess points or intermediate access network gateway nodes.
 42. A systemaccording to claim 39, characterized in that the radio access networkcomprises an UMTS or a GPRS or GSM access network (UTRAN;GERAN) withradio access network control nodes comprising RNCs and/or BSCs, BTSs,Node-Bs or that the access network comprises an Unlicensed Mobile AccessNetwork (UMA) with access network nodes.
 43. A system according to claim39, characterized in that location related information about one or moremobile user stations is provided from the radio access network controlnodes to the first network node automatically or according to a knownprocedure or upon request by the first network node.
 44. A systemaccording to claim 43, characterized in that a request from a firstnetwork node is defined so as to refer to one or more specific mobileuser stations or to mobile user stations fulfilling one or morecriteria.
 45. A system according to claim 43, characterized in that thelocation related information comprises one or more of information aboutthe geographical location of a number of given mobile user stations on agiven level, cell level, service area level, RA level or sub-cell level,information about the time zone in which a mobile user station currentlyis located, for mobile user stations for which a change of time zone isplausible and charging related information.
 46. A system according toclaim 43, characterized in that the first network node uses the LocationReporting Control procedure to request location related information of agiven mobile user station.
 47. A system according to claim 39,characterized in that the dedicated information elements is/are added tothe user plane messages, to one, to a limited number of, or to all GTP-Upackets, concerning such mobile user stations for which the first corenode has requested location related information.
 48. A system accordingto claim 39, characterized in that means are provided for adaptivelocation provisioning to a second core network node, said meanscomprising a client in the second core network node.
 49. A core networknode for a communications system supporting communication of packetdata, characterized in that it comprises means for establishing forwhich mobile user station(s) location related information is to becollected from the access network over which said mobile user stationsare connected to said core network means for collecting and storing saidlocation related information, and means for providing location relatedinformation to a second core network node acting as a gateway toexternal or third party controlled communication systems or serviceproviders, in one or more dedicated information elements added toexisting communication of user plane traffic messages between said firstcore network node and said second core network node.
 50. A core networknode according to claim 49, characterized in that it comprises an SGSNor a gateway node to a wireless access network.
 51. A core network nodeaccording to claim 49, characterized in that said means for providingthe location related information comprises means for adding saidinformation element or elements to all, to one or to a limited numberof, messages or GTP-U packets sent in the user plane, for theestablished mobile user station(s).
 52. A core network node according toclaim 49, characterized in that said means for providing locationrelated information are adapted to add said information to all trafficalmessages sent from mobile user stations for which the core network nodehas requested Location Reporting Control.
 53. A core network nodeaccording to claim 49, characterized in that it comprises means foradding said location related information to messages sent to the secondcore node when the location related information has changed for themobile user station.
 54. A core network node for a communications systemsupporting communication of packet data and acting as a gateway node toexternal or third party controlled communications system or serviceproviders, characterized in that it comprises means for collectinglocation related information for mobile user stations from a first corenetwork node supporting communication of data, said location relatedinformation is provided in one or more dedicated information elementsadded to existing communication of user plane traffic messages betweensaid first core network node and said second core network node, saidmeans comprising control means for, based on specified criteria,enabling adaptive collection of location related information for mobileuser stations for which the specified criteria are met and for enablingadaptive reporting of such location related information to external orthird party controlled data communications networks or serviceproviders.
 55. A core network node according to claim 54, characterizedin that it comprises a GGSN.
 56. A core network node according to claim54, characterized in that said criteria are mobile user station locationrelated.
 57. A core network node according to claim 56, characterized inthat the location related information comprises information about inwhich cell or service area a mobile user station is located or to whichcell or service area a mobile user station is moving/has moved and/orinformation about in which time zone a mobile user is located or achange of time zone, such location related information only beingcollected for mobile stations for which a change of time zones isplausible.
 58. A core network node according to claim 54, characterizedin that said control means comprises a Location Services Client allowingadaptive collection of location related information.
 59. A core networknode according to claim 54, characterized in that means are provided fortransferring said location related information to a GMLC allowing forlocation based service provisioning or location based charging, or to athird party service provider to allow said third party service providerto provide location based services.
 60. A method for providing a secondcore network node, acting as gateway to an external or third partycontrolled data communications system, with location related informationof one or more mobile user stations accessing the core network over anaccess network, characterized in that it comprises the steps of:establishing at least for which mobile user stations location relatedinformation is to be collected in a first network node; collecting saidlocation related information for said mobile user stations; storing saidlocation related information in storing means in or associated with saidfirst network node; arranging said location related information indedicated information element(s); adding said dedicated informationelement(s) to user plane traffic messages sent independently of saidinformation element from said first network node to the second corenetwork node.
 61. A method according to claim 60, characterized in thatthe step of adding information elements to messages comprises: addingthe information element(s) to all traffical packets sent in the userplane for the concerned mobile user stations.
 62. A method according toany one of claims 61, characterized in that it comprises the step of:adaptively reporting location related information comprisinggeographical location information and/or time zone information to allowfor location dependent rating or service provisioning on a per mobileuser station basis.